Repository navigation
[codex] Separate commercial distribution from Core - #120
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Issue and user impact
Commercial distribution code lived in public Core, but released Content Control Pro versions still depend on Core's license provider and updater key. Removing every shared path at once would make a Core-first rollout break Pro licensing and authenticated updates.
The mixed-version state must remain usable in either release order. The next Core release with active Pro below 1.3.0 keeps license management and authenticated Pro updates while exposing no installer, connection, or webhook behavior. Customers install Pro manually until Pro 1.3.0 is available.
Fix
Compatibility matrix
Validation
git diff --checkpassed.The repository-wide TypeScript/lint commands still expose pre-existing toolchain debt: TypeScript 6 rejects the existing deprecated
moduleResolution=node10/esModuleInterop=falseconfiguration, and the package lint command reports existing resolver/global/type parsing errors throughout the settings package.Related PRs